Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor everserver 2 #9777

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

frode-aarstad
Copy link
Contributor

@frode-aarstad frode-aarstad commented Jan 16, 2025

Issue
Resolves #9290

Approach
Short description of the approach

(Screenshot of new behavior in GUI if applicable)

  • PR title captures the intent of the changes, and is fitting for release notes.
  • Added appropriate release note label
  • Commit history is consistent and clean, in line with the contribution guidelines.
  • Make sure unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')

When applicable

  • When there are user facing changes: Updated documentation
  • New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
  • Large PR: Prepare changes in small commits for more convenient review
  • Bug fix: Add regression test for the bug
  • Bug fix: Create Backport PR to latest release

@frode-aarstad frode-aarstad self-assigned this Jan 16, 2025
@frode-aarstad frode-aarstad force-pushed the refactor-everserver-2 branch 2 times, most recently from 249e947 to d0b2ca4 Compare January 16, 2025 11:20
Copy link

codspeed-hq bot commented Jan 16, 2025

CodSpeed Performance Report

Merging #9777 will not alter performance

Comparing frode-aarstad:refactor-everserver-2 (dbee95a) with main (deeff70)

Summary

✅ 25 untouched benchmarks

@frode-aarstad frode-aarstad added the release-notes:maintenance Automatically categorise as maintenance change in release notes label Jan 17, 2025
Copy link
Collaborator

@oyvindeide oyvindeide left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, some minor comments and questions

src/everest/detached/jobs/everserver.py Outdated Show resolved Hide resolved
src/everest/detached/jobs/everserver.py Outdated Show resolved Hide resolved
tests/everest/test_detached.py Outdated Show resolved Hide resolved
tests/everest/test_logging.py Outdated Show resolved Hide resolved
tests/everest/test_everserver.py Outdated Show resolved Hide resolved
src/everest/detached/__init__.py Outdated Show resolved Hide resolved
@frode-aarstad frode-aarstad force-pushed the refactor-everserver-2 branch 3 times, most recently from 3d5df0c to 8334307 Compare January 22, 2025 14:04
run_model.run_experiment(evaluator_server_config)
self._exit_code = run_model.exit_code
except Exception:
self._exit_code = EverestExitCode.EXCEPTION
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we store/propagate the error exception message too so it can be passed back to the client?

@yngve-sk
Copy link
Contributor

looking good to me, only some questions/comments about error propagation for the endpoints

Copy link
Contributor

@yngve-sk yngve-sk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@frode-aarstad frode-aarstad merged commit cb0726d into equinor:main Jan 29, 2025
27 checks passed
@frode-aarstad frode-aarstad deleted the refactor-everserver-2 branch January 29, 2025 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes:maintenance Automatically categorise as maintenance change in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Split everserver functionality between starting server and submitting experiment
3 participants